home *** CD-ROM | disk | FTP | other *** search
- # This is the database for the auto connect feature of DP
- # You can define connect paths for your most used stations
- #
- # A definition can be made in three ways:
- # 1) basic path with frequency definition
- # 2) path using a yet learned basic path
- # 3) path using another of type 2)
- #
- # Type 1):
- # ID:CALL FREQ CALL1 CALL2 <..> CALL
- # e.g.:
- # Berlin:DB0BLO 438300 DB0BLO
- # or:
- # Berlin:DB0BLO 438450 DB0BLN DB0BLO
- # what means: when the trx is tuned to 438300 db0blo will be connected
- # directly, when it is tuned to 438450 first db0bln is connected and
- # then db0blo. Note that no 'via'-connect is generated, it is a true
- # two step connect. Assuming that you want to connect DB0BLO via DB0BLN
- # the definition requires a 'F>' to define that db0bln is a Level 2
- # digipeater:
- # Berlin:DB0BLO 438450 F>DB0BLN DB0BLO
- # If DB0BLO is a L2 - digipeater, type:
- # Berlin:DB0BLO 438450 F>DB0BLN F>DB0BLO
- # When connecting DB0BLO you won't remark a difference, but when this
- # fragment of path is used in another definiton (see below), a multiple
- # 'via'-connect is generated.
- #
- # Type 2)
- # The above learned path can be used for further paths. If, for example,
- # DB0BNO is accessible via DB0BLO, a definition would look like:
- # Berlin2:DB0BNO DB0BLO DB0BNO
- # Note that DP has the definitions for DB0BLO to connect either on 4538300 or
- # 438450, for both frequencies only one definition for db0bno ist necessary.
- #
- # Type 3)
- # is in fact the same as Type 2), you can refer to any given defintion to
- # build up a complete path:
- # Peter:DL9XYZ DB0BNO DL9XYZ-1
- #
- # DP uses those definitions when you start a connect with ALT-C , e.g.
- # ALT-C Peter <Return>
- #
- # Typing ALT-C <Return> will show you all current valid paths. You can
- # select one with the mouse.
- #
- # ---------------------------
- #
- # die pfadliste für dp
- # Der Aufbau ist relativ einfach gehalten:
- # ID:CALL FREQ CALL1 CALL2 CALL
- # also z.B.:
- # SE:DB0HHN 438175 DB0HHN
- # oder
- # SE:DB0HHN 430800 DB0BER DB0TOR DB0HHN
- # anstelle der Frequenzangabe kann auch ein schon 'gelerntes' Call/ID stehen,
- # also z.B.:
- # BWEST:DB0BLN 430800 DB0BER DB0BLN
- # HARZ:DB0TOR BWEST DB0TOR
- # SE:DB0HHN HARZ DB0HHN
- #
- # Die Pfadliste darf beliebig lang sein (wenn sie denn in den Speicher passt),
- # lediglich bei der Anzahl der Digis in einer Connectkette gibt es eine
- # Begrenzung.. DP meckert dann beim Connectversuch.
- #
- # Um einen Pfad auszuwählen, kann man sowohl Call als auch ID angeben
- # (nach ALT-C...). Also z.B.: ALT-C HARZ oder ALT-C DB0TOR
- #
- # Ab DP v 3.13 werden 'via'-Connects ermöglicht. Damit DP den Connect
- # möglichst effektiv bestimmen kann, sollte ein L2-Digi (dazu
- # zählen RMNC,Baycom,Falcon,Privat-Digis mit TNC und Repeatfunktion usw.,
- # aber NICHT TNN) mit einem führenden F> in der Connectkette angegeben
- # werden.
- # Beispiele:
- #
- # BWEST:DB0BLN 430800 DB0BER F>DB0BLN
- # BWEST:DB0BLN 438450 F>DB0BLN
- # BSUED:DB0BER 430800 DB0BER
- # BSUED:DB0BER BWEST DB0BER
- # HARZ2:DB0NID BWEST F>DB0NID
- # DB0RHN HARZ2 F>DB0RHN
- # DK0MAV HARZ2 DB0FC DK0MAV
- #
- # Connected man nun DK0MAV auf der QRG 430800, so sendet DP folgendes:
- # 'C DB0BER' , 'C DB0FC DB0BLN DB0NID' , 'C DK0MAV'
- #
- # gross/KLEINschrift ist egal.
- #
- # Ab hier die eigentlichen Definitonen (AENDERN!!!)
- #
- # Alter the below defintions!
-
- BWEST:DB0BLN 430800 DB0BER F>DB0BLN
- BWEST:DB0BLN 438450 F>DB0BLN
- BSUED:DB0BER 430800 DB0BER
- BSUED:DB0BER BWEST DB0BER
- HARZ2:DB0NID BWEST F>DB0NID
-
-